Method for controlling a device and machine module arrangement as well as an engineering system and runtime system for implementing the method

ABSTRACT

There is described an engineering systems and generating projects. The projects are used by runtime systems for the control of device and machine modular arrangements. The projects are not completely unmodifiable, instead an individualization layer is provided: particular data input possibilities for base data used by the runtime system are provided with an attribute, which gives whether the data entry in the project shall be unmodifiable or whether said entry may be optionally modifiable by the runtime system. A change is correspondingly optionally carried out with the runtime system. The actual core of the project, however does not need to be re-programmed such that a reversion to the engineering system is not necessary.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is the U.S. National Stage of International ApplicationNo. PCT/EP2006/068795, filed Nov. 23, 2006 and claims the benefitthereof. The International Application claims the benefits of Germanapplication No. 10 2005 062 810.9 DE filed Dec. 28, 2005, both of theapplications are incorporated by reference herein in their entirety.

FIELD OF INVENTION

The invention relates to a method for controlling a device and/ormachine module arrangement. It also relates to an engineering system forimplementing the method and a runtime system for implementing themethod.

BACKGROUND OF INVENTION

To control a device and machine module arrangement a so-called projectis generated, which is a combination of so-called machine objects, whichrepresent the devices and machine modules of the arrangement. Such aproject can include configuration data, parameterization data andprograms.

Such a project is generated by a programmer with the aid of anengineering system. On the target system, in other words in proximity tothe device and machine module arrangement, is a runtime system, as acounterpart to the engineering system, on which runtime system theproject runs in the manner of a computer program.

It is always important here for the project to be tailored to therespective device and machine module arrangement. The project must bebased on knowledge of the device and machine module types used.

Until now all the necessary basic data in the project had to bedetermined at the time of engineering. This includes for example theaddresses of the devices and modules (e.g. the so-called IP address ofan Ethernet interface) and the bus clock for timing signals by way of aclock-synchronous fieldbus used in the context of the arrangement. Alsoin certain instances the topology must be known in detail; even if thecomponents as such are known, in the case of a series arrangement of thedevices and modules for example, their sequence must also be known.

Determining this basic data is frequently cumbersome in day to dayoperation. With a real arrangement there can be slight deviations fromthe configured arrangement. For example when the production machine isincorporated in the end customer network, the address of a device maylook different or it may no longer be possible to use the configured busclock for certain application reasons.

Until now with repeated deployment of the engineering system the projecthad to be modified specifically for the respective situation. It wasthus always necessary to modify the entire project.

It is disadvantageous that on the one hand the engineering system has tobe deployed once again for adaptation to the device and machine modulearrangement present locally on the machine, when it does not necessarilyhave to be present locally itself. Also the creation of a project isassociated with significant outlay, so that it is unfortunate if changeshave to be made to the project. Also the local operators are often notable to operate the engineering system and to make the changes to theproject.

EP 1 548 527 A1 describes a control or regulation facility of a machinetool or production machine. User software is programmed in anengineering system. Application-specific macros are also created inaddition to the user software. The user software can be modified bymeans of the macro. Parameters and their parameter values can also bemodified by means of a macro.

EP 1 221 638 A2 also describes the use of macros in an automationsystem, with which it is possible to initiate a series of automaticconfiguration and parameterization processes.

SUMMARY OF INVENTION

An object of the invention is to specify a method, with which smallerchanges to the basic data can be managed more easily and with lessoutlay as well as more reliably for the inventory of, the actualproject. It is also an object to embody an engineering system and aruntime system correspondingly so that the method can be implemented.

The object is achieved by a method as claimed in an independent claim,an engineering system as claimed in a further independent claim and aclaimed runtime system.

According to the invention therefore when the project is being createdin the engineering system an attribute is assigned to data inputpossibilities provided in the project for the basic data, said attributeindicating whether the data input in the project is to be unmodifiable(in other words is to be determined once and then can no longer bemodified) or whether it can be individualized and can optionally stillbe modified in the runtime system (also including the instance where itis determined for the very first time in the runtime system). To adaptthe project to the device and machine module arrangement to becontrolled, corresponding inputs can then be made for theindividualizable data input possibilities in the runtime system.Generally inputs are actually made (or modified) for at least some ofthe individualizable data input possibilities.

The invention therefore creates a project, in which there is anadjustable individualization layer. A distinction is therefore madebetween the actual core of the project, which cannot be modified asbefore, and data inputs, for which individualization is possible. It istherefore possible to carry out small adaptations to the respectivespecific device and machine module arrangement locally in the context ofthe runtime system, so that it is not necessary to reprogram or modifythe actual project. The adaptation can therefore take place locally byway of operating means which are available at the machine and theengineering system therefore no longer has to be involved. Also theattribute, which relates to individualization, precisely determines thelimits of modifiability.

In one preferred embodiment when the project is being created a setpointbasic data set for a standard device and machine module arrangement isassumed, on the basis of which a first input is made for the data inputpossibilities, it being possible for the individualizable data inputs tobe modified in the runtime system, if the device and machine modulearrangement deviates from the standard device and machine modulearrangement.

The alternative to this is for no first input to be made initially inthe engineering system for the individualizable data input possibilitiesand for the corresponding data inputs only to be made in the runtimesystem. Generally the first alternative will be preferred, because asmany data inputs as possible of the basic data should be determined inthe context of the engineering system, so that as little as possibleremains to be done in the runtime system.

With both possibilities mentioned at least some of the individualizabledata inputs can be modified with user interaction or the data inputpossibilities can be carried out with user interaction. To this end theruntime system can wait for the initiative of the user wishing to changecertain data inputs correspondingly. Particularly when the data inputpossibilities are only used with user interaction, in other words inputsare made, it is possible for the runtime system to list all theindividualizable data input possibilities in the manner ofpredetermining a mask, to allow the user to make the input thus.

It is also possible in all instances, in particular it is additionallypossible for at least some of the inputs to be made automatically, forexample during connection to the device or machine module arrangement.There are known procedures for this, which are generally known as plugand play. In other words a device or machine module is connected and thesystem automatically identifies its type and further identifiers such asaddress, plug-in position, etc.

The general concept of data input possibilities can include a pluralityof possibilities. At least some of the individualizable data inputpossibilities can thus include addresses of bus users.

The addresses of bus users in particular are not always identical forotherwise identically structured arrangements. It is possible here touse individualization particularly elegantly to carry out an adaptationto the details of the respective arrangement without having to changethe entire project.

At least some of the individualizable data input possibilities can alsoinclude symbol names for addressing nodes in a network. In a network itis possible for a name to have been allocated already, so that it mustbe changed, when a new user is added. The names are then preferablyextendable in the presence of the attribute that they can beindividualized. In other words two devices with the same name can bedistinguished by a corresponding identifier, which is indicated in theextension of the name (e.g. by simple numbering).

At least some of the individualizable data input possibilities can alsoinclude the location of a specific device or a specific machine module.For example a project can be designed for a specific grouping of devicesand machine modules, whose topology does not however necessarily have tobe determined in detail. In the case of series arrangements specificallyit may be necessary to change the sequence of the individual devices andmachine modules. If the location is then attributed as individualizable,it is possible to include variations in the topology (for an otherwiseidentical device and machine module inventory).

In a further example the address information is derived from locallocation information. This is done for example by addressing a plug-inposition representing the location, in other words an interface, atwhich corresponding plug-in connections of the device or machine moduleare plugged in.

At least some of the individualizable data input possibilities caninclude a bus clock for a fieldbus. It is thus possible to take intoaccount the above-mentioned instance, where the bus clock is determinedin the project but subsequently proves not to be suitable. The bus clockproblem too can thus be resolved easily by way of individualization,with only the runtime system being deployed according to the inventionand there being no need to reprogram the project in the engineeringsystem.

A engineering system is designed so that the programmer can assign anattribute to at least some of the data input possibilities provided inthe project for the basic data, indicating whether the associated datainput can be individualized in a runtime system (i.e. can be input thereor can be modified if already input) or if it cannot be modified withoutchanging the project.

The runtime system can use projects generated with the aid of theengineering system. The runtime system is hereby designed to make inputsfor the data input possibilities characterized as individualizable andto modify an input that may be present.

The runtime system is suitable for the above-mentioned plug and playcontroller. In other words it is designed to identify connected devicesand machine modules and their identifiers, in particular address andplug-in position, automatically and make and/or modify the inputs asrequired based on the identification.

Instead of automatic identification it is also possible to display theinputs present for the data input possibilities characterized asindividualizable to an operator and to request new inputs from saidoperator. In the event that no inputs are yet present but the inputshave been inserted into these corresponding individualizable data inputpossibilities, only the new inputs are requested. To this end theruntime system can use suitable masks, on which the data inputpossibilities are listed.

BRIEF DESCRIPTION OF THE DRAWING

The invention is described below with reference to the FIGURE, whichshows in schematic form the method steps of the inventive method withthe inventive engineering system and the inventive runtime system.

DETAILED DESCRIPTION OF INVENTION

As is standard in the prior art, a project 12 is generated in anengineering system 10. The project is essentially a project like anyother, in other words machine objects are used and are combined to forma specific arrangement, which is intended to reflect a real device andmachine module arrangement. For subsequent control purposes it is alsonecessary to input specific basic data. The engineering system 10differs from conventional engineering systems in this respect. In thisinstance it is possible to determine which parts of the basic data willbe able to be modified subsequently without engineering. In other wordsdata input possibilities are assigned an attribute, which indicateswhether or not the data input is individualizable. Individualizable heremeans that the corresponding data inputs can be adapted at a later time,namely in the runtime system.

A first input is preferably made in the engineering system for the datainput possibilities, corresponding to a setpoint basic data set(default). In the inventive project therefore a so-calledindividualization layer 14 results, in other words a group of data inputpossibilities, which can be individualized.

The project 12 is now loaded into a runtime system 16. The runtimesystem 16 is located locally at the device and machine modulearrangement to be controlled and must in some instances be adaptedindividually to conditions there. Deviations from the setpoint basicdata set must therefore be detected. To this end it is necessary toaccess the individualization layer 14. The core inventory of the project12 is not modified in this process.

According to a first possibility an HMI client (Human Machine InterfaceClient) 18 is provided. For example the runtime system 16 canpredetermine a mask, in which all the data inputs of theindividualization layer 14 are displayed, in other words all the datainputs that are characterized as individualizable. In the context of themask a user can then confirm the setting according to the setpoint basicdata set, in other words the first input, by pressing the input key orcan make a change to the corresponding input, for example by way of akeyboard (not shown).

In one variant, which can be predetermined as an addition oralternative, a plug and play modality 20 is provided. The runtime system16 is connected to a specific device and machine module arrangement andidentifies different characteristics of the connected devices andmachine modules. These include their type and address; the topology canalso be known via the plug and play modality 20. It is correspondinglypossible for the individualization layer 14 to be adapted automaticallyto the conditions identified via the plug and play modality 20 in theruntime system 16, in other words the corresponding data inputs can bemodified as required.

The same is also possible with the aid of a user program (AWP) 22. Userprograms are known within the context of the control of device andmachine module arrangements. In the present instance theindividualization layer 14 can be accessed so that certain data inputs,whose attribute is that they can be individualized, can be modified.

The three modalities 18, 20 and 22 can be present simultaneouslyindependently of one another or may only be provided as alternatives toone another.

It is a characteristic of the invention that the actual core of theproject 12 is not changed. Changes only take place in a previouslyprecisely determined individualization layer 14. The changes are made bythe runtime system 16. The engineering system 10 is no longer requiredat these subsequent times.

In the context of the individualization layer 14 it is possible todetect variations of the device and machine module arrangement relatingto its addressing, relating to the topology (location of individualmachine modules for example) or even relating to a bus clock for afieldbus.

The invention claimed is:
 1. A computerized method for controlling adevice and machine module arrangement, comprising: combining machineobjects associated with the device and machine modules in an engineeringsystem by an operator to form a project comprising computer programcode, wherein the project is deployed for the automatic control of thearrangement by a runtime system executable with a computer, and whereinthe project requires certain basic computer-readable data for thecontrol of the arrangement; providing an attribute when the project isbeing created in the engineering system, wherein the attribute comprisesa computer-readable attribute and is assigned to computer-readable datainput possibilities provided in the project for the basic dataindicating whether the data input in the project is to be unmodifiableor whether the data input is individualizable and where necessary canstill be modified in the runtime system; defining in the project anadjustable individualization layer, which is distinct from a core of theproject; limiting modifications of individualizable data inputs only tothe adjustable individualization layer and the core of the projectremaining unmodifiable; and providing computer-readable data inputpossibilities for the individualizable data inputs so that, when theruntime system is executed by the computer, an adapting of the projectis performed to control the device and machine module arrangement,wherein the adapting of the project is based on said modifications ofthe individualizable data inputs, which are limited only to theadjustable individualization layer and without modifying the core of theproject and thus without having to reprogram the project.
 2. The methodas claimed in claim 1, wherein when the project is being created, asetpoint basic data set is assumed for a standard device and machinemodule arrangement, according to which a first input is made for thedata input possibilities, it being possible to modify theindividualizable data inputs in the runtime system if the device andmachine module arrangement deviates from the standard device and machinemodule arrangement.
 3. The method as claimed in claim 2, wherein atleast some of the individualizable data inputs can be modified with userinteraction.
 4. The method as claimed in claim 2, wherein at least someof the individualizable data inputs are modified automatically.
 5. Themethod as claimed in claim 3, wherein at least some of theindividualizable data inputs are modified automatically.
 6. The methodas claimed in claim 1, wherein no first input is made in the engineeringsystem for the individualizable data input possibilities, and whereinthe corresponding inputs are only made in the runtime system.
 7. Themethod as claimed in claim 6, wherein inputs are made with userinteraction for the individualizable data input possibilities.
 8. Themethod as claimed in claim 6, wherein at least some of the inputs aremade automatically for the individualizable data input possibilities. 9.The method as claimed in claim 7, wherein at least some of the inputsare made automatically for the individualizable data inputpossibilities.
 10. The method as claimed in claim 1, wherein at leastsome of the individualizable data input possibilities include addressesof bus users.
 11. The method as claimed in claim 1, wherein at leastsome of the individualizable data input possibilities include symbolnames for nodes in a network, wherein the names are extendable in thepresence of the attribute that they are capable to be individualized.12. The method as claimed in claim 1, wherein at least some of theindividualizable data input possibilities include the location of aspecific device or a specific machine module.
 13. The method as claimedin claim 12, wherein the location is included by addressing a plug-inposition representing the location.
 14. The method as claimed in claim1, wherein at least some of the individualizable data inputpossibilities include a bus clock for a fieldbus.
 15. An engineeringsystem for controlling a device and machine module arrangement,comprising: a device to generate a project comprising computer programcode for controlling the device and machine module arrangement bycombining machine objects by a programmer, wherein as part of theproject the programmer additionally inputs computer-readable basic datafor the project as required for the control operation; and an attributeassigner so that the programmer can assign a respectivecomputer-readable attribute to at least some data input possibilitiesprovided in the project, the respective attribute indicating whether ornot an associated data input can be individualized in a runtime systemexecutable by a computer; an adjustable individualization layer definedin the project, the adjustable individualization layer being distinctfrom a core of the project, wherein modifications of individualizabledata inputs are limited only to the adjustable individualization layer,and wherein the core of the project remains unmodifiable, wherein theruntime system is executed by the computer so that the project isadapted to control the device and machine module arrangement, whereinadaptation of the project is based on said modifications of theindividualizable data inputs, which are limited only to the adjustableindividualization layer and without modifications to the core of theproject and thus without having to reprogram the project.
 16. Theengineering system as claimed in claim 15, wherein the associated datais inputted in the runtime system or modified in the runtime system. 17.A runtime system executable with a computer for implementing acomputerized method to control a device and machine module arrangement,comprising: a project comprising computer program code, wherein machineobjects associated with device and machine modules are combined in anengineering system by an operator to form the project, wherein theproject is deployed for the automatic control of the arrangement by aruntime system, wherein the project requires certain basiccomputer-readable data for the control of the arrangement, wherein anattribute is provided when the project is created in the engineeringsystem, wherein the attribute comprises a computer-readable attributeand is assigned to computer-readable data input possibilities providedin the project for the basic data indicating whether the data input inthe project is to be unmodifiable or whether the data input isindividualizable and where necessary can still be modified in theruntime system; an adjustable individualization layer defined in theproject, the adjustable individualization layer being distinct from acore of the project wherein modifications of individualizable datainputs are limited only to the adjustable individualization layer andthe core of the project remains unmodifiable; and computer-readableinputs for the data input possibilities characterized asindividualizable, wherein the runtime system is executed by the computerso that the project is adapted to control the device and machine modulearrangement, wherein adaptation of the project is based on saidmodifications of the individualizable data inputs, which are limitedonly to the adjustable individualization layer and without modificationsto the core of the project and thus without having to reprogram theproject.
 18. The runtime system as claimed in claim 17, wherein theruntime system identifies connected devices and machine modules andtheir identifiers automatically, and wherein the inputs as requiredbased on the identification are modified.
 19. The runtime system asclaimed in claim 18, wherein an address and a plug-in position ofconnected devices and machine modules are identified.
 20. The runtimesystem as claimed in claim 17, wherein inputs present for the data inputpossibilities characterized as individualizable are displayed, andwherein new inputs are requested from an operator.